Remove historical documentation#2822
Conversation
Head branch was pushed to by a user without write access
oleg-nenashev
left a comment
There was a problem hiding this comment.
I would keep Security Considerations at least. "In some cases non-admin users can contribute to JCasC exports if they have some permissions (e.g. agent/view configuration or credentials management)," is still relevant IMHO. The compatibility ones can be removed indeed, while keeping the actual behavior.
Leaving thee decision to the current maintainers so no strong vote
Reading the docs it all seems related to the security issue. The agent view one is people putting variables in to get secrets out but those are escaped for a long time. |
Replaced the TODO placeholder in secrets.adoc with a reference to the published Jenkins Security Advisory for SECURITY-1446 (CVE-2019-10362). The advisory documents the variable interpolation vulnerability in previously exported configurations and the fix introduced in JCasC 1.25, which aligns with the behavior described in this section.
Your checklist for this pull request
🚨 Please review the guidelines for contributing to this repository.